Instead if littering ifdef's across the code, use a single API and
initialize different pools only once.

Signed-off-by: Chaitanya Tata <[email protected]>
(cherry picked from commit ab9c531)

This reverts commit 3e9dffb.
Though this works fine, when CONFIG_ASSERT=y the spinlock validation
fails as the underlying code though uses OSAL spinlock APIs is not ready

* sleeping with spinlock held
* multiple threads taking the same spinlock (might work on UP, but not
  on SMP on the same CPU)

Revert this for now, till the underyling is robust.

Signed-off-by: Chaitanya Tata <[email protected]>
(cherry picked from commit 9693852)

The revert for some reason didn't do a full revert, fix the lock
variable.

Signed-off-by: Chaitanya Tata <[email protected]>
(cherry picked from commit 1fe2369)

This reverts commit 331f27b.

Signed-off-by: Ajay Parida <[email protected]>

Support to configure BSS max idle period at runtime.

To avoid big churn (net_mgmt 64bit), this commit should be reverted on
the next upmerge.

Signed-off-by: Ajay Parida <[email protected]>

These are helpful for logging in data-path, not to overwhelm the
console but still keep the user informed about the issues.

This is similar to printk_ratelimited in Linux kernel.

Add only basic build tests for now.

Upstream PR #: 93536

[To avoid release notes churn, marking as noup]

Signed-off-by: Chaitanya Tata <[email protected]>

Add the ratelimtied variants for data path debug.

Upstream PR #: 93536

Signed-off-by: Chaitanya Tata <[email protected]>

As this is the hot data path, use a rate limited warning variant.

Upstream PR #: 93282

Signed-off-by: Chaitanya Tata <[email protected]>

In case of a busy environment and if STA is far, then we see many
retries for the frames that cause the RPU to be awake though host has
de-asserted wakeup_now signal, this leads to WDT interrupt and host
thinks that it has given sleep opportunity to RPU and initiates a
recovery.

To handle this, increase the sleep opportunity window to 5s to cover all
the retries, this solves the false recovery problem. While at it, also
increase the range, no reason to limit to lower window. And update the
help text with the warning about power consumption.

Upstream PR #: 93662

Signed-off-by: Chaitanya Tata <[email protected]>

…i for keep-alive bit set"

This reverts commit 3350eb2.

Signed-off-by: Chaitanya Tata <[email protected]>

…ure flags

Pull fix to fail if no compatible feature is found.

Signed-off-by: Chaitanya Tata <[email protected]>
(cherry picked from commit fcffe8f)

Pull fix for double pulling of raw TX header, fixes warnings seen during
tests.

Upstream PR #: 93085

Signed-off-by: Chaitanya Tata <[email protected]>

Add missing binding to fix the device tree warning.

Signed-off-by: Chaitanya Tata <[email protected]>
(cherry picked from commit 1495e2e)

the nRF connect device tree extension shows below warning:
'Property not mentioned in "nordic,nrf-pinctrl:child"'.

Fix this by applying the property to both groups separately.

Signed-off-by: Chaitanya Tata <[email protected]>
(cherry picked from commit 613ec82)

… groups

Add a newline between child nodes.

Signed-off-by: Chaitanya Tata <[email protected]>
(cherry picked from commit 86690f2)